failure 205:

Serialization Failed

location
trace	/var/opt/lsb/test/olver-core/2013-01-21_10-20-40/util_assert_verrx_scenario.utz (util_assert_verrx_scenario.utt), line 18803
occurence
scenario	util_assert_verrx_scenario
properties
kind	SERIALIZATION_FAILED

Stimuli & reactions in the serialization:
id and signature	channel	timestamp	parameter
a) specification verrx_spec( CallContext context, IntT eval, CString fmt, List arguments, CString *stderrAsFile )	1		CallContext context = [pid=17706,thr=b74ed6c0]
			IntT eval = -1
			CString * @fmt = abcd
			CString * fmt = abcd
			List * @arguments = < 1200 >
			List * arguments = < 1200 >
			CString * @stderrAsFile = /tmp/olver/util_assert_verrx_scenario/stderrAsFile.txt
			CString * stderrAsFile = /tmp/olver/util_assert_verrx_scenario/stderrAsFile.txt
b) reaction *err_processTerminated( void )	1		result = (ExitReturnType *) struct ExitReturnType { name=verrx, context=[pid=17706,thr=b74ed6c0] }

Serialization:
#	series	coverage	branch
1	1. verrx_spec (a)	C_Priority	Process with high priority
	2. err_processTerminated (b)
	Requirement failed: {verrx.41} a formatted error message on the standard error stream

similar known bug(s)
The verrx() function shall display a formatted error message on the standard error stream. According to LSB, the formatted error message, the last component of the program name, a colon character, a space and a newline character shall be output. But on the target machine colon character, and a space are not output after the formatted error message. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488.